FYI:Routing Host Not Routing Mail for Nonrouting Host
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:Routing Host Not Routing Mail for Nonrouting Host
DOCUMENT ID#:FYI.S.MHS100
DATE:29OCT92
PRODUCT:Message Handling Service
PRODUCT VERSION:1.5
SUPERSEDES:NA
SYMPTOM
Primary host is not routing nonrouting hosts mail.
ISSUE/PROBLEM
Routing HOSTA is declared as the "Primary Hub" on nonrouting HOSTB. When HOSTA connects INET, it puts mail into the HOSTB's queues directory but does not route HOSTB's mail. HOSTA is configured to log onto HOSTB's server as a user with sufficient rights to process the mail.
SOLUTION
The workstation that runs MHS was also used to run a utility that attaches to HOSTB's server as "GUEST." When the utility is terminated, it does not log out the workstation. When HOSTA connects to HOSTB, it used the existing mapped drive and "GUEST" does not have sufficient rights to route the mail. Logging out of HOSTB's server before running MHS solved the problem.
FYI:MHS Connectivity with Stat MUX
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:MHS Connectivity with Stat MUX
DOCUMENT ID#:FYI.S.MHS101
DATE:27OCT92
PRODUCT:Message Handling Service
PRODUCT VERSION:1.5
SUPERSEDES:NA
SYMPTOM
Configuring MHS to transfer messages over multiplexed lines
ISSUE/PROBLEM
How can MHS be configured to transfer messages over a multiplexed (MUX) line?
SOLUTION
In general, MHS can handle up to transfer speed up to 9600 baud. The default speed should be set to match the data line's capability. For example, a 64 KB data line which has been divided into 8 channels of 8 KB each will be able to transmit at 2400 baud.
The modem type should be set to NULLMDM (null modem). Identical modem and speed declarations must be set in "Set up Transport Server" and in "Set up this host." No speed sensing is recommended for null modem connections.
Because no telephone number is associated with a multiplexed data line, the remote host dialing string can be set to "," representing a pause. MHS is designed to operate with a transmission frame of eight data bits, no parity, one stop bit. Note that XON/XOFF flow control should be disabled. MHS uses the XON and XOFF characters as packet delimiters. Also, attachment control on the MUX should be set to unqualified, as opposed to options such as modem, DTR toggle, and DTR no toggle.
FYI:SMFSEAL.EXE Causes Workstation to Hang
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:SMFSEAL.EXE Causes Workstation to Hang
DOCUMENT ID#:FYI.S.MHS102
DATE:10NOV92
PRODUCT:Message Handling Service
PRODUCT VERSION:1.5 Rev B
SUPERSEDES:NA
SYMPTOM
When SMFSEAL is used to send messages to MHS, the workstation hangs.
ISSUE/PROBLEM
Revision B of SMFSEAL.EXE for both Network and Personal has a bug.
SOLUTION
Use Revision A of SMFSEAL. If necessary, a user can obtain Revision A by contacting Novell Technical Support at 800-NETWARE (801-429-5588).
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
When an MHS 1.5 host and an MHS 1.2 host are communicating asynchronously, periodically the asynchronous connection is dropped with an informational message, "Preparing remote mail for new MHS version, please call later."
Neither of the MHS hosts were upgraded or patched during this time.
ISSUE/PROBLEM
This is an incompatibility between MHS 1.5 and MHS 1.2. As long as the same host is always the calling host, the asynchronous communication will work properly. This problem will occur every time the receiving host becomes the calling host.
SOLUTION
Novell is not planning to fix this problem. The MHS 1.2 user should upgrade their mail server to NetWare Global Messaging, a later version of MHS, or the configuration needs to be modified so that one specific MHS host is always the calling host.
FYI:MHS Does Not Work with COM3/COM4
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:MHS Does Not Work with COM3/COM4
DOCUMENT ID#:FYI.S.MHS104
DATE:10NOV92
PRODUCT:Message Handling Service
PRODUCT VERSION:1.5
SUPERSEDES:NA
SYMPTOM
MHS is not working when COM3 or COM4 ports are set.
ISSUE/PROBLEM
MHS works properly with a modem on COM1 or COM2. However, when that modem is moved to COM3 or COM4, it stops working.
SOLUTION
The COM port settings must be set according to the table shown below. Other settings for COM ports are nonstandard and are not supported by MHS. MHS does auto-detect which bus type is being used.
┌──────┬─────┬─────────┬──────────┐
│ PORT │ IRQ │ ADDRESS │ BUS TYPE │
├──────┼─────┼─────────┼──────────┤
│ COM1 │ 4 │ 3F8 │ ISA │
│ COM2 │ 3 │ 2F8 │ ISA │
│ COM3 │ 4 │ 3E8 │ ISA │
│ COM4 │ 3 │ 2E8 │ ISA │
│ COM1 │ 4 │ 3F8 │ MCA │
│ COM2 │ 3 │ 2F8 │ MCA │
│ COM3 │ 3 │ 3220 │ MCA │
│ COM4 │ 3 │ 3228 │ MCA │
└──────┴─────┴─────────┴──────────┘
If the COM ports are configured as described above and problems still exist, verify that there are no active devices on the associated COM port. COM1/3 and COM2/4 cannot be connected to active devices at the same time.
FYI:Problem Installing "M15xx3.ZIP" Patches
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:Problem Installing "M15xx3.ZIP" Patches
DOCUMENT ID#:FYI.S.MHS105
DATE:11NOV92
PRODUCT:Message Handling Service
PRODUCT VERSION:1.5x Revision B
SUPERSEDES:NA
SYMPTOM
An attempt to apply the patch contained in M15xx3.ZIP to a 1.5x Rev B host failed with the following error message:
┌────────────────────────────┐
│File is not a valid MHSN.OVR│
└────────────────────────────┘
ISSUE/PROBLEM
The file PATCH.COM was in the MHS\SYS directory.
SOLUTION
Removing PATCH.COM from this directory resulted in the successful installation of the patch. PATCH.COM is not required by the 1.5x Rev B host and does not need to be put back into the MHS\SYS directory.
FYI:Remapping TN3270 Telnet Escape Character
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:Remapping TN3270 Telnet Escape Character
DOCUMENT ID#:FYI.S.LWP67
DATE:30OCT92
PRODUCT:TN3270 for LAN WorkPlace
PRODUCT VERSION:3.13a
SUPERSEDES:NA
SYMPTOM
The Telnet Escape character (Ctrl ]) used to get to a TN-CMD prompt from a session with a remote host does not work with a French keyboard.
ISSUE/PROBLEM
It is possible to perform the same function by entering Ctrl $. The $ key on a French keyboard is located in the same position as the ] key on a U.S. keyboard.
SOLUTION
To remap a local feature key, a keyid entry is required in the SNATERMK file. Because no keyid is available for the Telnet Escape character, it cannot be remapped; consequently, French users must continue to use Ctrl $ to access TN3270 emulator's command mode.
FYI:Improper Display in Vi in ANSI Mode (TNVT220)
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:Improper Display in Vi in ANSI Mode (TNVT220)
DOCUMENT ID#:FYI.S.LWP68
DATE:02NOV92
PRODUCT:TNVT220
PRODUCT VERSION:4.01
SUPERSEDES:NA
SYMPTOM
In vi after entering a sample string, the "sample string" display looks like the following:
s@a@m@p@l@e@ s@t@r@i@n@g@
ISSUE/PROBLEM
The symptom is a result of problems with the TNVT220 - ANSI.SYS driver.
SOLUTION
Instead of using ANSI.SYS on the workstation, use the NANSI.SYS driver that can be obtained from anonymous archive sites (such as WUARCHIVE.WUSTL.EDU). This driver fixes the problem.
FYI:LAN WorkPlace for DOS and 3270 LAN Workstation
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:LAN WorkPlace for DOS and 3270 LAN Workstation
DOCUMENT ID#:FYI.S.LWP69
DATE:02NOV92
PRODUCT:LAN WorkPlace for DOS and 3270 LAN Workstation
PRODUCT VERSION:4.x and 1.1
SUPERSEDES:NA
SYMPTOM
When using LAN WorkPlace 4.x and 3270 LAN workstation at the same time in Windows, the Host Presenter setup font selection gives you APL font selections that displays garbage on the screen.
ISSUE/PROBLEM
The 3270 LAN workstation dynamically adds the APL fonts in several sizes and can give a GP Fault in module USER.EXE by Host Presenter.
SOLUTION
Do not select any APL fonts for a Host Presenter session. The TCPIP connection should remain stable allowing 3270 and TCP/IP connectivity.
FYI:Cannot Ping Using a 3c503 Board
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:Cannot Ping Using a 3c503 Board
DOCUMENT ID#:FYI.S.LWP70
DATE:03NOV92
PRODUCT:LAN WorkPlace for DOS
PRODUCT VERSION:4.01
SUPERSEDES:NA
SYMPTOM
The user can only ping himself.
ISSUE/PROBLEM
The 3c503 board passed diagnostics, and all the drivers loaded properly. When trying to ping, 64 KB packets of unknown type are sent out instead of an ARP broadcast or ICMP echo packets.
SOLUTION
Disabling the memory on the 3c503 resolved the problem. The 3COM diagnostics are not completely accurate.
FYI:ODI and Packet Drivers
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:ODI and Packet Drivers
DOCUMENT ID#:FYI.S.LWP71
DATE:06NOV92
PRODUCT:LAN WorkPlace for DOS
PRODUCT VERSION:4.01
SUPERSEDES:NA
SYMPTOM
The user was unable to get ODI to run over NDIS.
ISSUE/PROBLEM
1.How to run Packet Driver applications over ODI drivers?
2.How to run ODI applications (such as LAN WorkPlace) over Packet Drivers?
SOLUTION
1.Get the ODIPKT.ZIP file from NetWire, NOVLIB Lib 13.
2.Get the PDETHR.ZIP file from NetWire, NOVLIB Lib 13.
Novell does not support either of these, but users can be made aware of them.
FYI:Procomm Network v2.0 Fails in Interrupt Line 14 Mode
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:Procomm Network v2.0 Fails in Interrupt Line 14 Mode
DOCUMENT ID#:FYI.S.LWP72
DATE:09NOV92
PRODUCT:LAN WorkPlace for DOS
PRODUCT VERSION:4.01
SUPERSEDES:NA
SYMPTOM
Interrupt Line 14h error
ISSUE/PROBLEM
When configured for Interrupt line 14 and run with LAN WorkPlace for DOS v4.01, the Procomm Network v2.0 fails with the following error:
┌────────────────────────────────────────┐
│Int 14h interface not operating properly│
└────────────────────────────────────────┘
SOLUTION
Configure Procomm for BAPI interface instead of Interrupt line 14.
FYI:LAN WorkPlace for DOS Using LANSUP with 3C503 NIC
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:LAN WorkPlace for DOS Using LANSUP with 3C503 NIC
DOCUMENT ID#:FYI.S.LWP73
DATE:12NOV92
PRODUCT:LAN WorkPlace for DOS
PRODUCT VERSION:4.01
SUPERSEDES:NA
SYMPTOM
Unable to ping the RS6000
ISSUE/PROBLEM
The user is trying to access RS6000 using LAN WorkPlace for DOS v4.01 with LANSUP.COM using a 3C503 Ethernet board. He is unable to ping the RS6000 after loading the necessary LAN support drivers (PROTMAN.EXE, ELNKII.DOS, DXMA0MOD.SYS, DXME0.SYS).
SOLUTION
Use ODINSUP.COM in place of LANSUP.COM to accomplish the same thing. ODINSUP.COM provides a direct channel for LAN WorkPlace and TCP/IP to the link support layer without going through the *MOD.SYS layers as in LANSUP. Explanation of this can be found in the September 1992 issue of NetWare Application Notes.
FYI:QEdit - LAN WorkPlace for DOS NFS Incompatibility Warning
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:QEdit - LAN WorkPlace for DOS NFS Incompatibility Warning
DOCUMENT ID#:FYI.S.LWP75
DATE:12NOV92
PRODUCT:LAN WorkPlace for DOS NFS
PRODUCT VERSION:4.01
SUPERSEDES:NA
SYMPTOM
QEdit opens .* files on the LAN WorkPlace for DOS NFS as empty files. Exiting from the editor does not help and the file disappears.
ISSUE/PROBLEM
QEdit does not interpret and recognize the file with the name as translated by NFS client. QEdit does search for the file. When the file is not found, it opens a new one for writing, overwriting the old one. This does not happen with files that have natively DOS compatible filenames (before translation).
SOLUTION
Avoid using this editor on files residing on NFS client volumes. So far two other editors, Mortice Kern vi for DOS and Borland's Brief, do not seem to generate the same problem.
FYI:Using LAN WorkPlace with the IBM C/2 Compiler
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:Using LAN WorkPlace with the IBM C/2 Compiler
DOCUMENT ID#:FYI.S.LWP76
DATE:16NOV92
PRODUCT:LAN WorkPlace for OS/2
PRODUCT VERSION:3.0
SUPERSEDES:NA
SYMPTOM
The user is unable to build LAN WorkPlace applications using the IBM C/2 compiler.
ISSUE/PROBLEM
How can one build LAN WorkPlace applications using the IBM C/2 compiler for OS/2 v2.0?
SOLUTION
Before compiling, make the following changes to Novell's header files:
1.Change all "int" declarations to "short".
2.Change all pointer declarations from "*" or "far *" to "* _Seg16".
3.Change all function declarations from "pascal far" to "_Far16 _Pascal".
Compile with -Sm switch.
FYI:LAN Workplace for OS/2 Hanging at TCPIP.OS2 Driver
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this77 information.)
TITLE:LAN Workplace for OS/2 Hanging at TCPIP.OS2 Driver
DOCUMENT ID#:FYI.S.LWP77
DATE:18NOV92
PRODUCT:LAN WorkPlace for OS/2
PRODUCT VERSION:3.0
SUPERSEDES:NA
SYMPTOM
After loading OS/2 v2.0 and the NetWare Requester v2.0 for OS/2, the user loaded the LAN WorkPlace for OS/2 v3.0. He placed the NET.CFG file in the NETWARE subdirectory. When the user rebooted the computer, the OS/2 booted to the point of loading the Novell IFS Requester v2.0 driver and hung at the TCPIP.OS2 driver in the CONFIG.SYS file.
ISSUE/PROBLEM
The NET.CFG file must be in he ROOT directory. Even if the directory where it is located is in the DPATH, it will not find it.
SOLUTION
It appears that the LAN WorkPlace software requires the NET.CFG file be located in the ROOT. After placing the NET.CFG file in the ROOT, the system booted correctly.
FYI:Windows Netware Shell Problem
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:Windows Netware Shell Problem
DOCUMENT ID#:FYI.S.LZFN6
DATE:11NOV92
PRODUCT:LANalyzer for NetWare
PRODUCT VERSION:1.0
SUPERSEDES:NA
SYMPTOM
In the File Manager, the network drives do not display the server name or directory. The Browse option under Disk, Network-Drive connections crashes Windows.
ISSUE/PROBLEM
Configuration:
Using EMSNETX.COM from the NetWire patch:XMSXKB.PAT, with the NE2000.COM that ships with LANalyzer for NetWare v1.0.
The problem is related to the shell.
SOLUTION
Use the NETX.COM that ships with LANalyzer for NetWare.
FYI:LANalyzer for NetWare and TBMI2.COM Driver Conflict
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:LANalyzer for NetWare and TBMI2.COM Driver Conflict
DOCUMENT ID#:FYI.S.LZFN7
DATE:24NOV92
PRODUCT:LANalyzer for NetWare
PRODUCT VERSION:1.0
SUPERSEDES:NA
SYMPTOM
ERROR - "UNABLE TO START SERVER CHECKING"
ISSUE/PROBLEM
The user installed the LANalyzer for NetWare software on his laptop computer with a NE2000 card and started Windows. He then stared the LANalyzer for NetWare application and received the error about starting the server checking.
SOLUTION
1.Make sure that the ODI drivers are the latest versions.
2.Disable all the drivers in the AUTOEXEC.BAT file by using the remark command.
3.Load each driver manually, one at a time.
4.Do not load the TBMI2.COM driver. TBMI2.COM is required for some Windows applications that do not run correctly under Enhanced mode. Below are the modifications required to allow use of the driver for those applications.
5.Modify the LZNET.BAT file to read:
TBMI2 -u
LZFN.EXE
TBMI2
This unloads the driver TBMI2 and then starts LANalyzer for NetWare. When you exit the LZFN software, it reloads the driver.
FYI:LANalyzer for NetWare Using Intel's EtherExpress NIC
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:LANalyzer for NetWare using Intel's EtherExpress NIC
DOCUMENT ID#:FYI.S.LZFN8
DATE:12NOV92
PRODUCT:LANalyzer for NetWare
PRODUCT VERSION:1.0
SUPERSEDES:NA
SYMPTOM
While the user tried to load DI.COM, the system displayed the following error message:
┌──────────────────────────┐
│NO SUPPORTED DRIVERS FOUND│
└──────────────────────────┘
ISSUE/PROBLEM
Configuration:
■INTEL EtherExpress network board
■EXPODI.COM
This error results from trying to use a driver that does not support promiscuous mode.
SOLUTION
Although the EtherExpress board is not currently on the list of certified boards for LANalyzer for NetWare, it will work if you get the most recent ODI driver from Intel.
FYI:LANtern Services Manager and Permanent Swap Files
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:LANtern Services Manager and Permanent Swap Files
DOCUMENT ID#:FYI.S.LSM6
DATE:11NOV92
PRODUCT:LANtern Services Manager
PRODUCT VERSION:1.3b
SUPERSEDES:NA
SYMPTOM
LANtern Services Manager collects data for a few weeks, then stops with the error "disk is full" when 90 MB is still available.
ISSUE/PROBLEM
Reconfiguring Windows so it would not use a permanent swap file resolved the problem.
SOLUTION
Suggested workaround: Place the permanent swap file on a different partition.
FYI:Conflict between NMM and Another NLM (MDA.NLM)
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:Conflict between NMM and Another NLM (MDA.NLM)
DOCUMENT ID#:FYI.S.NSM8
DATE:18NOV92
PRODUCT:NetWare Services Manager
PRODUCT VERSION:1.1
SUPERSEDES:N/A
SYMPTOM
The user was unable to get the NetWare Services Manager Performance Gauges to work correctly on one of the servers. The user was in Netware Services Manager and had the View All NetWare Servers and the specific server selected. Then when the user selected the "Performance" option, then "Gauges" option, and MEMORY gauge with percentages, the screen changed to reflect the selection and prompted that it was obtaining the information. Then, the screen switched to a white screen with no display of the gauges.
ISSUE/PROBLEM
Another NLM was causing a conflict.
SOLUTION
The user removed the MDA.NLM (dated 05-28-91) from the AUTOEXEC.NCF file and removed the NLM from memory.
FYI:NetWare Services Manager Map Updates
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE:NetWare Services Manager Map Updates
DOCUMENT ID#:FYI.S.NSM9
DATE:09NOV92
PRODUCT:NetWare Services Manager
PRODUCT VERSION:1.1
SUPERSEDES:NA
SYMPTOM
Viewing the internet map shows more than one network number. Opening the segment displays several router icons attached to the same segment.
ISSUE/PROBLEM
Autodiscovery has not completed and may take several hours to find all routers and display them properly on the internet map.
SOLUTION
If the internet map displays (changed) on the title bar, go under the View menu and select the "Update" option. This will change the locational internet map. Also let autodiscovery continue until the segments on the internet map show one network address.